IEEE Recommended Practice for Architectural Description of Software - Intensive Systems
ثبت نشده
چکیده
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. Abstract: This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions. A conceptual framework for architectural description is established. The content of an architectural description is defined. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of …
منابع مشابه
Introducing IEEE Standard 1471: Recommended Practice for Architectural Description for Software Intensive Systems
IEEE Standard 1471 is the Recommended Practice for Architectural Description for Software Intensive Systems, developed by the IEEE’s Architecture Working Group (AWG) under the sponsorship of the Software Engineering Standards Committee of IEEE. The draft Recommended Practice was produced between 1995 and 1998 by a group of approximately thirty participants, and over 140 international reviewers....
متن کاملIEEE Std 1471-2000, IEEE Recommended Practice forArchitectural Description ofSoftware-Intensive Systems
This recommended practice addresses the activities of the creation, analysis, and sustainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions . A conceptual framework for architectural description is established. The content of an architectural description is defined. Annexes provide the rationale for key concepts an...
متن کاملUsing the UML for Architectural Description
There is much interest in using the Unified Modeling Language (UML) for architectural description – those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architect...
متن کاملView Composition as a First-Class Concept in Architectural Descriptions
Our position is that architectural descriptions lack composition of views, preventing a proper separation of concerns. This position took shape from experiences with building several complex distributed software systems. Our claim is that view composition should be a first-class entity in architectural descriptions. As a first step, we propose an extension of the conceptual model of IEEE Recomm...
متن کاملIeee Std 1471 and beyond * Content Requirements on Ads
Overview I describe the key contributions of IEEE Std 1471 to the discipline of software architecture representation. After reviewing the contributions of IEEE 1471, I discuss how we (the community interested in Software Architecture) may build upon the foundation provided by IEEE 1471 to continue to improve and disseminate techniques for architectural description. (Although three pages is insu...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2000